docs: clarify MCP client credentials vs Mintlify API keys#6162
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
approved these changes
Jun 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a clarifying note to the MCP client credentials section explaining that Mintlify REST API keys cannot authenticate to the search MCP server.
Changes
<Note>callout inai/model-context-protocol.mdxdistinguishing MCP client credentials from admin/assistant API keys, and pointing to the existing client credential creation flow.Context
Recent assistant conversations show users asking whether the Mintlify API key works for MCP authentication. The MCP page documents OAuth and client credentials thoroughly but never explicitly contrasts them with the REST API keys, leading to confusion.
Note
Low Risk
Documentation-only clarification with no product or auth behavior changes.
Overview
Adds a
<Note>callout in the Client credentials section of the Search MCP docs (English, Spanish, and French) so readers do not treat Mintlify REST API keys as MCP auth.The note states that MCP client credentials are separate from Mintlify API keys—admin and assistant keys only work against the Mintlify REST API and cannot authenticate to the search MCP server. It directs programmatic callers to create a client credential on the MCP server dashboard page and exchange it for an access token using the steps that follow.
Reviewed by Cursor Bugbot for commit 729e73e. Bugbot is set up for automated code reviews on this repo. Configure here.